The Juniper PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance bound to the appropriate physical or logical interfaces to maintain traffic separation between all MPLS L3VPNs.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-254064	JUEX-RT-000920	SV-254064r997537_rule		High

Description
The primary security model for an MPLS L3VPN infrastructure is traffic separation. The service provider must guarantee the customer that traffic from one VPN does not leak into another VPN or into the core, and that core traffic must not leak into any VPN. Hence, it is imperative that each CE-facing interface can only be associated to one VRF—that alone is the fundamental framework for traffic separation.

Description

The primary security model for an MPLS L3VPN infrastructure is traffic separation. The service provider must guarantee the customer that traffic from one VPN does not leak into another VPN or into the core, and that core traffic must not leak into any VPN. Hence, it is imperative that each CE-facing interface can only be associated to one VRF—that alone is the fundamental framework for traffic separation.

STIG	Date
Juniper EX Series Switches Router Security Technical Implementation Guide	2024-06-10

Details

Check Text ( C-57516r844223_chk )
Review the design plan for deploying L3VPN and VRF-lite. Review all CE-facing interfaces and verify that the proper VRF is defined. [edit interfaces] { description "To customer 1"; unit { family inet { address /; } family inet6 { address /; } } } [edit routing-instances] { description "To customer 1"; instance-type vrf; interface .; route-distinguisher ; vrf-target ; vrf-table-label; protocols { ospf { area { interface .; } } } } Note: In L3 VPN, the CE router forms an adjacency with the PE router (OSPF in the example). If any VRFs are not bound to the appropriate physical or logical interface, this is a finding.

Check Text ( C-57516r844223_chk )

Review the design plan for deploying L3VPN and VRF-lite.

Review all CE-facing interfaces and verify that the proper VRF is defined.
[edit interfaces]

{
description "To customer 1";
unit {
family inet {
address /;
}
family inet6 {
address /;
}
}
}

[edit routing-instances]
{
description "To customer 1";
instance-type vrf;
interface .;
route-distinguisher ;
vrf-target ;
vrf-table-label;
protocols {
ospf {
area {
interface .;
}
}
}
}

Note: In L3 VPN, the CE router forms an adjacency with the PE router (OSPF in the example).

If any VRFs are not bound to the appropriate physical or logical interface, this is a finding.

Fix Text (F-57467r844224_fix)
Configure the PE router to have each VRF bound to the appropriate physical or logical interfaces to maintain traffic separation between all MPLS L3VPNs. set interfaces description <"appropriate description"> set interfaces unit family inet address / set interfaces unit family inet6 address / set routing-instances description <"appropriate description"> set routing-instances instance-type vrf set routing-instances interface . set routing-instances route-distinguisher set routing-instances vrf-target set routing-instances vrf-table-label set routing-instances protocols ospf area interface .

Fix Text (F-57467r844224_fix)

Configure the PE router to have each VRF bound to the appropriate physical or logical interfaces to maintain traffic separation between all MPLS L3VPNs.

set interfaces description <"appropriate description">
set interfaces unit family inet address /
set interfaces unit family inet6 address /

set routing-instances description <"appropriate description">
set routing-instances instance-type vrf
set routing-instances interface .
set routing-instances route-distinguisher
set routing-instances vrf-target
set routing-instances vrf-table-label
set routing-instances protocols ospf area interface .